UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

SLEM 5 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-261411 SLEM-05-653015 SV-261411r996646_rule Medium
Description
Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in SLEM 5 audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured SLEM 5.
STIG Date
SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide 2024-06-04

Details

Check Text ( C-65140r996098_chk )
Verify SLEM 5 produces audit records with the following commands:

> systemctl is-active auditd.service
active

> systemctl is-enabled auditd.service
enabled

If the service is not active or not enabled, this is a finding.
Fix Text (F-65048r996099_fix)
Enable SLEM 5 auditd service by using the following commands:

> sudo systemctl enable auditd.service
> sudo systemctl start auditd.service